Application model in Menu Studio is very simple. Each application consists of individual fields, which are called pages. Basically, pages are blank fields for the information to be placed on them. The transitions between the pages are possible with the event prossessing, which we will discuss a little bit latter.

To place information on the page, to create connection between the pages, to make the component dynamic or interactive, and to allow the assessment of an application to some other elements of the operational sphere, all that is possible with the help of components. They are to be placed on the pages. There are 21 components in the given program, which are divided at six groups:

• Text
  
• Graphics
  
• Shapes
  
• ButtonClassisc
  
• ButtonImage
  
• Players

Components are closely connected with the concept of events. There are two types of events:

Mouse click on the component
Mouse moving over the component
(Note: event processing is not provided for all the components)

After an event has occurred (user has moved a mouse over a component or clicked on it), the event processor appears and an application performs the desired action. Two kinds of actions are present in Menu Studio:

Action when mouse is clicked on the component
Action when mouse is moved over the component

Here is basically the whole conception of the Menu Studio, structural scheme of which looks like this:
Page-Component-Event-Action